Methods and user interfaces for sharing audio

ABSTRACT

While an electronic device is connected to a first external device, display a first user interface including a first affordance. Detect an input selecting the first affordance. In response to detecting the input corresponding to selection of the first affordance, initiate a process to provide audio data concurrently with the first external device and a second external device different from the first external device. After initiating the process to provide audio data concurrently to the first external device and a second external device, detect an indication that a physical proximity between the electronic device and the second external device satisfies a proximity condition. In response to detecting the indication that the physical proximity between the electronic device and the second external device satisfies the proximity condition, display a second user interface indicating that the physical proximity between the electronic device and the second external device satisfies the proximity condition.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/583,994, titled “METHODS AND USER INTERFACES FOR SHARING AUDIO,”filed on Sep. 26, 2019, which claims priority to U.S. Provisional PatentApplication Ser. No. 62/855,897, titled “METHODS AND USER INTERFACES FORSHARING AUDIO,” filed on May 31, 2019, the contents of each of which arehereby incorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for sharing audio data.

BACKGROUND

Electronic devices can play various types of media that include audio,such as music tracks, podcasts, audio books, and videos. Modernelectronic devices can provide audio data via wireless connections toaudio output devices such as wireless speakers and wireless headphones.

BRIEF SUMMARY

Some techniques for sharing audio data using electronic devices,however, are generally cumbersome and inefficient. For example, someexisting techniques use a complex and time-consuming user interface,which may include multiple key presses or keystrokes. Existingtechniques require more time than necessary, wasting user time anddevice energy. This latter consideration is particularly important inbattery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for sharing audio data.Such methods and interfaces optionally complement or replace othermethods for sharing audio data. Such methods and interfaces reduce thecognitive burden on a user and produce a more efficient human-machineinterface. For battery-operated computing devices, such methods andinterfaces conserve power and increase the time between battery charges.

Example methods are disclosed herein. An example method includes, at anelectronic device with a display device, while the electronic device isconnected to a first external device via a communication link, whereinthe electronic device is configured to provide audio data to the firstexternal device via the communication link, displaying, via the displaydevice, a first user interface including a first affordance; detectingan input corresponding to selection of the first affordance; in responseto detecting the input corresponding to selection of the firstaffordance, initiating a process to provide audio data concurrently withthe first external device and a second external device different fromthe first external device; after initiating the process to provide audiodata concurrently to the first external device and a second externaldevice, detecting an indication that a physical proximity between theelectronic device and the second external device satisfies a proximitycondition; and in response to detecting the indication that the physicalproximity between the electronic device and the second external devicesatisfies the proximity condition, displaying a second user interfaceindicating that the physical proximity between the electronic device andthe second external device satisfies the proximity condition.

Example non-transitory computer-readable storage media are describedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device, the one ormore programs including instructions for: while the electronic device isconnected to a first external device via a communication link, whereinthe electronic device is configured to provide audio data to the firstexternal device via the communication link, displaying, via the displaydevice, a first user interface including a first affordance; detectingan input corresponding to selection of the first affordance; in responseto detecting the input corresponding to selection of the firstaffordance, initiating a process to provide audio data concurrently withthe first external device and a second external device different fromthe first external device; after initiating the process to provide audiodata concurrently to the first external device and a second externaldevice, detecting an indication that a physical proximity between theelectronic device and the second external device satisfies a proximitycondition; and in response to detecting the indication that the physicalproximity between the electronic device and the second external devicesatisfies the proximity condition, displaying a second user interfaceindicating that the physical proximity between the electronic device andthe second external device satisfies the proximity condition.

Example transitory computer-readable storage media are described herein.An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while the electronic device is connected toa first external device via a communication link, wherein the electronicdevice is configured to provide audio data to the first external devicevia the communication link, displaying, via the display device, a firstuser interface including a first affordance; detecting an inputcorresponding to selection of the first affordance; in response todetecting the input corresponding to selection of the first affordance,initiating a process to provide audio data concurrently with the firstexternal device and a second external device different from the firstexternal device; after initiating the process to provide audio dataconcurrently to the first external device and a second external device,detecting an indication that a physical proximity between the electronicdevice and the second external device satisfies a proximity condition;and in response to detecting the indication that the physical proximitybetween the electronic device and the second external device satisfiesthe proximity condition, displaying a second user interface indicatingthat the physical proximity between the electronic device and the secondexternal device satisfies the proximity condition.

Example electronic devices are described herein. An example electronicdevice includes a display device; one or more processors; and memorystoring one or more programs configured to be executed by the one ormore processors, the one or more programs including instructions for:while the electronic device is connected to a first external device viaa communication link, wherein the electronic device is configured toprovide audio data to the first external device via the communicationlink, displaying, via the display device, a first user interfaceincluding a first affordance; detecting an input corresponding toselection of the first affordance; in response to detecting the inputcorresponding to selection of the first affordance, initiating a processto provide audio data concurrently with the first external device and asecond external device different from the first external device; afterinitiating the process to provide audio data concurrently to the firstexternal device and a second external device, detecting an indicationthat a physical proximity between the electronic device and the secondexternal device satisfies a proximity condition; and in response todetecting the indication that the physical proximity between theelectronic device and the second external device satisfies the proximitycondition, displaying a second user interface indicating that thephysical proximity between the electronic device and the second externaldevice satisfies the proximity condition.

An example electronic device includes a display device; means for, whilethe electronic device is connected to a first external device via acommunication link, wherein the electronic device is configured toprovide audio data to the first external device via the communicationlink, displaying, via the display device, a first user interfaceincluding a first affordance; means for detecting an input correspondingto selection of the first affordance; means for, in response todetecting the input corresponding to selection of the first affordance,initiating a process to provide audio data concurrently with the firstexternal device and a second external device different from the firstexternal device; means for, after initiating the process to provideaudio data concurrently to the first external device and a secondexternal device, detecting an indication that a physical proximitybetween the electronic device and the second external device satisfies aproximity condition; and means for, in response to detecting theindication that the physical proximity between the electronic device andthe second external device satisfies the proximity condition, displayinga second user interface indicating that the physical proximity betweenthe electronic device and the second external device satisfies theproximity condition.

An example method includes, at an electronic device with a displaydevice: while the electronic device is connected to a first externaldevice via a communication link, wherein the electronic device isconfigured to provide audio data to the first external device via thecommunication link, detecting an indication that a physical proximitybetween the electronic device and a second external device, differentfrom the first external device, satisfies a proximity condition; inresponse to detecting the indication that the physical proximity betweenthe electronic device and the second external device satisfies theproximity condition, displaying, via the display device, a first userinterface including a first affordance; detecting an input correspondingto selection of the first affordance; and in response to detecting theinput corresponding to selection of the first affordance, initiating aprocess to provide audio data concurrently with the first externaldevice and the second external device.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while the electronic device is connected toa first external device via a communication link, wherein the electronicdevice is configured to provide audio data to the first external devicevia the communication link, detecting an indication that a physicalproximity between the electronic device and a second external device,different from the first external device, satisfies a proximitycondition; in response to detecting the indication that the physicalproximity between the electronic device and the second external devicesatisfies the proximity condition, displaying, via the display device, afirst user interface including a first affordance; detecting an inputcorresponding to selection of the first affordance; and in response todetecting the input corresponding to selection of the first affordance,initiating a process to provide audio data concurrently with the firstexternal device and the second external device.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while the electronic device is connected toa first external device via a communication link, wherein the electronicdevice is configured to provide audio data to the first external devicevia the communication link, detecting an indication that a physicalproximity between the electronic device and a second external device,different from the first external device, satisfies a proximitycondition; in response to detecting the indication that the physicalproximity between the electronic device and the second external devicesatisfies the proximity condition, displaying, via the display device, afirst user interface including a first affordance; detecting an inputcorresponding to selection of the first affordance; and in response todetecting the input corresponding to selection of the first affordance,initiating a process to provide audio data concurrently with the firstexternal device and the second external device.

An example electronic device includes a display device; one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: while the electronic device is connected toa first external device via a communication link, wherein the electronicdevice is configured to provide audio data to the first external devicevia the communication link, detecting an indication that a physicalproximity between the electronic device and a second external device,different from the first external device, satisfies a proximitycondition; in response to detecting the indication that the physicalproximity between the electronic device and the second external devicesatisfies the proximity condition, displaying, via the display device, afirst user interface including a first affordance; detecting an inputcorresponding to selection of the first affordance; and in response todetecting the input corresponding to selection of the first affordance,initiating a process to provide audio data concurrently with the firstexternal device and the second external device.

An example electronic device includes a display device; means for, whilethe electronic device is connected to a first external device via acommunication link, wherein the electronic device is configured toprovide audio data to the first external device via the communicationlink, detecting an indication that a physical proximity between theelectronic device and a second external device, different from the firstexternal device, satisfies a proximity condition; means for, in responseto detecting the indication that the physical proximity between theelectronic device and the second external device satisfies the proximitycondition, displaying, via the display device, a first user interfaceincluding a first affordance; means for detecting an input correspondingto selection of the first affordance; and means for, in response todetecting the input corresponding to selection of the first affordance,initiating a process to provide audio data concurrently with the firstexternal device and the second external device.

An example method includes, at an electronic device with a displaydevice: while a first connection condition is satisfied with respect tothe electronic device, a first external device, and a second externaldevice, wherein the electronic device is configured to provide audiodata to the first external device when connected to the first externaldevice and to provide audio data to the second external device whenconnected to the second external device, receiving a request to displaya first volume control affordance; in response to receiving the requestto display the first volume control affordance, displaying the firstvolume control affordance; detecting an input corresponding to selectionof the first volume control affordance; and in response to detecting theinput corresponding to selection of the first volume control affordance,displaying a user interface including: in accordance with adetermination that a second connection condition is satisfied withrespect to the second external device, displaying a second volumecontrol affordance that, when selected, adjusts a volume level of thefirst external device and a third volume control affordance that, whenselected, adjusts a volume level of the second external device; and inaccordance with a determination that the second connection condition isnot satisfied with respect to the second external device, displaying afourth volume control affordance that, when selected, adjusts a volumelevel of the first external device, without displaying a volume controlaffordance for adjusting the volume level of the second external device.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while a first connection condition issatisfied with respect to the electronic device, a first externaldevice, and a second external device, wherein the electronic device isconfigured to provide audio data to the first external device whenconnected to the first external device and to provide audio data to thesecond external device when connected to the second external device,receiving a request to display a first volume control affordance; inresponse to receiving the request to display the first volume controlaffordance, displaying the first volume control affordance; detecting aninput corresponding to selection of the first volume control affordance;and in response to detecting the input corresponding to selection of thefirst volume control affordance, displaying a user interface including:in accordance with a determination that a second connection condition issatisfied with respect to the second external device, displaying asecond volume control affordance that, when selected, adjusts a volumelevel of the first external device and a third volume control affordancethat, when selected, adjusts a volume level of the second externaldevice; and in accordance with a determination that the secondconnection condition is not satisfied with respect to the secondexternal device, displaying a fourth volume control affordance that,when selected, adjusts a volume level of the first external device,without displaying a volume control affordance for adjusting the volumelevel of the second external device.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while a first connection condition issatisfied with respect to the electronic device, a first externaldevice, and a second external device, wherein the electronic device isconfigured to provide audio data to the first external device whenconnected to the first external device and to provide audio data to thesecond external device when connected to the second external device,receiving a request to display a first volume control affordance; inresponse to receiving the request to display the first volume controlaffordance, displaying the first volume control affordance; detecting aninput corresponding to selection of the first volume control affordance;and in response to detecting the input corresponding to selection of thefirst volume control affordance, displaying a user interface including:in accordance with a determination that a second connection condition issatisfied with respect to the second external device, displaying asecond volume control affordance that, when selected, adjusts a volumelevel of the first external device and a third volume control affordancethat, when selected, adjusts a volume level of the second externaldevice; and in accordance with a determination that the secondconnection condition is not satisfied with respect to the secondexternal device, displaying a fourth volume control affordance that,when selected, adjusts a volume level of the first external device,without displaying a volume control affordance for adjusting the volumelevel of the second external device.

An example electronic device includes a display device; one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: while a first connection condition issatisfied with respect to the electronic device, a first externaldevice, and a second external device, wherein the electronic device isconfigured to provide audio data to the first external device whenconnected to the first external device and to provide audio data to thesecond external device when connected to the second external device,receiving a request to display a first volume control affordance; inresponse to receiving the request to display the first volume controlaffordance, displaying the first volume control affordance; detecting aninput corresponding to selection of the first volume control affordance;and in response to detecting the input corresponding to selection of thefirst volume control affordance, displaying a user interface including:in accordance with a determination that a second connection condition issatisfied with respect to the second external device, displaying asecond volume control affordance that, when selected, adjusts a volumelevel of the first external device and a third volume control affordancethat, when selected, adjusts a volume level of the second externaldevice; and in accordance with a determination that the secondconnection condition is not satisfied with respect to the secondexternal device, displaying a fourth volume control affordance that,when selected, adjusts a volume level of the first external device,without displaying a volume control affordance for adjusting the volumelevel of the second external device.

An example electronic device includes a display device; means for whilea first connection condition is satisfied with respect to the electronicdevice, a first external device, and a second external device, whereinthe electronic device is configured to provide audio data to the firstexternal device when connected to the first external device and toprovide audio data to the second external device when connected to thesecond external device, receiving a request to display a first volumecontrol affordance; means for, in response to receiving the request todisplay the first volume control affordance, displaying the first volumecontrol affordance; means for detecting an input corresponding toselection of the first volume control affordance; and means for, inresponse to detecting the input corresponding to selection of the firstvolume control affordance, displaying a user interface including: inaccordance with a determination that a second connection condition issatisfied with respect to the second external device, displaying asecond volume control affordance that, when selected, adjusts a volumelevel of the first external device and a third volume control affordancethat, when selected, adjusts a volume level of the second externaldevice; and in accordance with a determination that the secondconnection condition is not satisfied with respect to the secondexternal device, displaying a fourth volume control affordance that,when selected, adjusts a volume level of the first external device,without displaying a volume control affordance for adjusting the volumelevel of the second external device.

An example method includes, at an electronic device with a displaydevice: while displaying a first user interface including controls foran audio media application, receiving a request to display a userinterface for selecting one or more devices from which audio from theaudio media application is to be output; in response to receiving therequest to display a user interface for selecting one or more devicesfrom which audio from the audio media application is to be output,displaying a second user interface including: in accordance with adetermination that a source electronic device is connected to a firstexternal device and a second external device, different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, displaying a first affordance that, whenselected, causes audio data from the audio media application to beprovided concurrently to the first external device and the secondexternal device; and in accordance with a determination that the sourceelectronic device is connected to the first external device andconfigured to provide audio data from the audio media application to thefirst external device without concurrently providing audio data from theaudio media application to another external device, displaying a secondaffordance that, when selected, causes audio data from the audio mediaapplication to be provided solely to the first external device.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while displaying a first user interfaceincluding controls for an audio media application, receiving a requestto display a user interface for selecting one or more devices from whichaudio from the audio media application is to be output; in response toreceiving the request to display a user interface for selecting one ormore devices from which audio from the audio media application is to beoutput, displaying a second user interface including: in accordance witha determination that a source electronic device is connected to a firstexternal device and a second external device, different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, displaying a first affordance that, whenselected, causes audio data from the audio media application to beprovided concurrently to the first external device and the secondexternal device; and in accordance with a determination that the sourceelectronic device is connected to the first external device andconfigured to provide audio data from the audio media application to thefirst external device without concurrently providing audio data from theaudio media application to another external device, displaying a secondaffordance that, when selected, causes audio data from the audio mediaapplication to be provided solely to the first external device.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display device, the one or more programsincluding instructions for: while displaying a first user interfaceincluding controls for an audio media application, receiving a requestto display a user interface for selecting one or more devices from whichaudio from the audio media application is to be output; in response toreceiving the request to display a user interface for selecting one ormore devices from which audio from the audio media application is to beoutput, displaying a second user interface including: in accordance witha determination that a source electronic device is connected to a firstexternal device and a second external device, different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, displaying a first affordance that, whenselected, causes audio data from the audio media application to beprovided concurrently to the first external device and the secondexternal device; and in accordance with a determination that the sourceelectronic device is connected to the first external device andconfigured to provide audio data from the audio media application to thefirst external device without concurrently providing audio data from theaudio media application to another external device, displaying a secondaffordance that, when selected, causes audio data from the audio mediaapplication to be provided solely to the first external device.

An example electronic device includes a display device; one or moreprocessors; and memory storing one or more programs configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: while displaying a first user interfaceincluding controls for an audio media application, receiving a requestto display a user interface for selecting one or more devices from whichaudio from the audio media application is to be output; in response toreceiving the request to display a user interface for selecting one ormore devices from which audio from the audio media application is to beoutput, displaying a second user interface including: in accordance witha determination that a source electronic device is connected to a firstexternal device and a second external device, different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, displaying a first affordance that, whenselected, causes audio data from the audio media application to beprovided concurrently to the first external device and the secondexternal device; and in accordance with a determination that the sourceelectronic device is connected to the first external device andconfigured to provide audio data from the audio media application to thefirst external device without concurrently providing audio data from theaudio media application to another external device, displaying a secondaffordance that, when selected, causes audio data from the audio mediaapplication to be provided solely to the first external device.

An example electronic device includes a display device; means for whiledisplaying a first user interface including controls for an audio mediaapplication, receiving a request to display a user interface forselecting one or more devices from which audio from the audio mediaapplication is to be output; and means for, in response to receiving therequest to display a user interface for selecting one or more devicesfrom which audio from the audio media application is to be output,displaying a second user interface including: in accordance with adetermination that a source electronic device is connected to a firstexternal device and a second external device, different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, displaying a first affordance that, whenselected, causes audio data from the audio media application to beprovided concurrently to the first external device and the secondexternal device; and in accordance with a determination that the sourceelectronic device is connected to the first external device andconfigured to provide audio data from the audio media application to thefirst external device without concurrently providing audio data from theaudio media application to another external device, displaying a secondaffordance that, when selected, causes audio data from the audio mediaapplication to be provided solely to the first external device.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for sharing audio data, thereby increasing the effectiveness,efficiency, and user satisfaction with such devices. Such methods andinterfaces may complement or replace other methods for sharing audiodata.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6R illustrate exemplary user interfaces in accordance with someembodiments.

FIG. 7 illustrates an exemplary method in accordance with someembodiments.

FIG. 8 illustrates an exemplary method in accordance with someembodiments.

FIGS. 9A-9E illustrate exemplary user interfaces in accordance with someembodiments.

FIG. 10 illustrates an exemplary method in accordance with someembodiments.

FIGS. 11A-11F illustrate exemplary user interfaces in accordance withsome embodiments.

FIG. 12 illustrates an exemplary method in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for sharing audio data. In some embodiments, while aprimary device is connected to a first wireless device (e.g., a pair ofwireless headphones paired to the primary device), the primary deviceenters a sharing mode in response to selection of a share audioaffordance. In response to a second wireless device (e.g., anotheruser's pair of wireless headphones) being brought into close proximityof the primary device, a process is initiated for the primary device toshare audio data with the second external device while concurrentlyproviding the same audio data to the first external device. In someembodiments, the audio data is temporarily shared with the secondexternal device. This allows a user to easily share audio wirelesslywith another person so that they can listen to the audio together, e.g.,without requiring a preexisting or persistent relationship between theprimary device and the second external device. In some embodiments, thesharing process is initiated by bringing the second external device intoproximity with the primary device, without initially requiring selectionof the share audio affordance. Exemplary techniques for controlling thevolume of the first and second external devices while sharing audio dataare also described. For example, the primary device can provide a volumecontrol interface based on the configuration of the connection with thesecond external device (e.g., whether the second external device isbeing controlled by a third external device (e.g., a phone)). Exemplarytechniques for selecting a device for playing audio are also described.For example, an audio media user interface provides options (e.g.,affordances) to select where to play music based on whether the primarydevice is sharing audio. Such techniques can reduce the cognitive burdenon a user who share audio data, thereby enhancing productivity. Further,such techniques can reduce processor and battery power otherwise wastedon redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for sharing audio data.FIGS. 6A-6R illustrate exemplary user interfaces for sharing audio data.FIGS. 7-8 are flow diagrams illustrating methods of sharing audio datain accordance with some embodiments. The user interfaces in FIGS. 6A-6Rare used to illustrate the processes described below, including theprocesses in FIGS. 7-8. FIGS. 9A-9E illustrate exemplary user interfacesfor sharing audio data. FIG. 10 is a flow diagram illustrating methodsof sharing audio data in accordance with some embodiments. The userinterfaces in FIGS. 9A-9E are used to illustrate the processes describedbelow, including the processes in FIG. 10. FIGS. 11A-11F illustrateexemplary user interfaces for sharing audio data. FIG. 12 is a flowdiagram illustrating methods of sharing audio data in accordance withsome embodiments. The user interfaces in FIGS. 11A-11F are used toillustrate the processes described below, including the processes inFIG. 12.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.1 lac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2) optionally include an up/down buttonfor volume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module,    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications. International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including methods 700, 800,1000, and 1200 (FIGS. 7, 8, 10, and 12). A computer-readable storagemedium can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. In some examples,the storage medium is a transitory computer-readable storage medium. Insome examples, the storage medium is a non-transitory computer-readablestorage medium. The non-transitory computer-readable storage medium caninclude, but is not limited to, magnetic, optical, and/or semiconductorstorages. Examples of such storage include magnetic disks, optical discsbased on CD, DVD, or Blu-ray technologies, as well as persistentsolid-state memory such as flash, solid-state drives, and the like.Personal electronic device 500 is not limited to the components andconfiguration of FIG. 5B, but can include other or additional componentsin multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button), inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6R illustrate exemplary user interfaces for sharing audio data,in accordance with some embodiments. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe processes in FIGS. 7-8.

FIG. 6A illustrates electronic device 600 and device 625 (also referredto as “Taylor's Earbuds”). In some embodiments, device 600 is device100, 300, or 500. Device 600 has a display device 602 depicted as atouch-sensitive display (e.g., touchscreen 504). Device 625 isconfigured to connect to device 600 and output audio (e.g.,human-audible sound waves) based on audio data received from device 600via communication link C1. In the embodiment illustrated in FIG. 6A,communication link C1 is a wireless (e.g., Bluetooth) connection. Insome embodiments, communication link C1 is a wired connection. In someembodiments, device 625 includes one or more features (e.g., audiocircuitry 110, speaker 111, microphone 113) of device 100, device 300,or device 500. In some embodiments, device 625 is a wireless speaker, orany device configured to connect to device 600 and output audio based onaudio data received from device 600. As illustrated in FIG. 6A, device625 is a pair of wireless earbuds consisting of earbud 625 a and earbud625 b. In the embodiment illustrated in FIG. 6A, although device 625 isa compound device that includes two physically separate earbuds, earbud625 a and earbud 625 b operate together as one device. In someembodiments, device 625 has a primary earbud that connects with device600 and a secondary earbud that communicates with the primary earbud andreceives audio signals from device 600 via the primary component. Insome embodiments, earbud 625 a and earbud 625 b are each connected todevice 600, but are treated by device 600 as a single external device.

In FIG. 6A, device 600 displays user interface 604, including audiomedia user interface 604 a. Audio media user interface 604 a includescurrent audio indicator 604 a-1, which includes information about anaudio application (e.g., an open audio application) associated withdevice 600, such as a device providing audio output (“Taylor'sEarbuds”), track name (“Track 1”), and artist name (“DJ Appleseed”).Audio media user interface 604 a includes affordances 604 a-2, 604 a-3,604 a-4, 604 a-5, and 604 a-6. Affordances 604 a-2, 604 a-3, 604 a-5correspond to respective audio devices, and when selected, provide audioto the selected device. In FIG. 6A, the check mark on affordance 604 a-3indicates that device 625 (“Taylor's Earbuds”) is the currently selectedaudio device, consistent with current audio indicator 604 a-1. Volumeaffordance 604 a-6 can be selected to adjust a volume level for thecurrently selected audio device.

Share audio affordance 604 a-4 can be selected to initiate a process forsharing audio data with another device, while concurrently providingaudio via a currently selected audio device (e.g., device 625). Forexample, sharing audio allows device 600 to create a temporaryconnection with the device of another user so that the two users canlisten to the same audio together at the same time, but without creatinga persistent or permanent association with the other user's device(e.g., without pairing device 600 with the other user's device, asdiscussed in more detail below).

In FIG. 6A, device 600 detects input 610 a (e.g., a tap) correspondingto selection of share audio affordance 604 a-4. In response to detectinginput 610 a, device 600 initiates a process to provide audio dataconcurrently with device 625 and a second external device. In theembodiment illustrated in FIG. 6B, the process includes displaying userinterface 606. User interface 606 includes user interface card 606 awith instructions 606 a-1 for how to share audio data with anotherdevice (e.g., another pair of wireless headphones or earbuds).Instructions 606 a-1 explain that audio can be shared by bringinganother pair of wireless headphones close to device 600. User interfacecard 606 a includes graphical element 606 a-2, which represents a device(or type of device) with which device 600 can share audio data ifbrought close to device 600. In this way, device 600 informs a user ofpotential devices or products with which audio data can be shared ifbrought close to device 600. In some embodiments, device 600 displaysrepresentations of more than one device with which device 600 can share.In FIG. 6C, device 600 displays graphical element 606 a-3, whichrepresents another with which device 600 can share audio data if broughtclose to device 600. Device 600 can display graphical elements ofpotential devices (e.g., graphical elements 606 a-2 and 606 a-3) invarious ways (e.g., concurrently or sequentially). As shown in FIG. 6C,device 600 replaces graphical element 606 a-2 with graphical element 606a-3 on user interface 606.

As indicated by instructions 606 a-1, device 600 can use thesatisfaction of a proximity condition to share audio data with anotherdevice, while concurrently providing audio data (e.g., the same audiodata) with device 625. The use of proximity of one device to anotherdevice can be used as a clear indicator that a user would like toperform some action (e.g., invoke an interface, share audio data) on oneor both of the devices. For example, this can prevent a waste of deviceresources by avoiding excessive user input (e.g., to navigate one ormore menus on a device display) in order perform a function. Moreover,this can save the user time as well, for example, by reducing the numberof user inputs required to perform a function (e.g., invoke an interfaceon a display, share audio data).

FIG. 6C illustrates an exemplary view of a scenario that includes device650 (also referred to as “Chance's Earbuds”) at a relatively longdistance away from the device 600. Device 650 is configured to connectto device 600 and output audio (e.g., human-audible sound waves) basedon audio data received from device 600. In some embodiments, device 650includes one or more features (e.g., audio circuitry 110, speaker 111,microphone 113) of device 100, 300, 500, or 625. In some embodiments,device 650 is a wireless speaker, or any device configured to connect todevice 600 and output audio based on audio data received from device600. As illustrated in FIG. 6C, device 650 is a pair of wireless earbudsconsisting of earbud 650 a, earbud 650 b, and case 650 c. In someembodiments, case 650 c interfaces with earbud 650 a and earbud 650 b toinitialize connection with device 600 (e.g., as described below withreference to FIG. 6E) and/or perform other operations associated withearbud 650 a and earbud 650 b (e.g., charging). In the embodimentillustrated in FIG. 6C, earbud 650 a, earbud 650 b, and case 650 coperate together as one single device and are treated by device 600 as asingle device.

In the embodiment illustrated in FIG. 6C, device 600 is associated withthe same user (e.g., Taylor) as device 625 and is paired with device625. In some embodiments, two devices are paired if they have apersistent association with each other and are configured to exchangedata via a communication link. For example, device 625 remainsassociated with device 600 when communication link C1 between thedevices is not currently active (e.g., device 600 will attempt toautomatically reconnect with device 625 if a connection is lost ordevice 600 shares common persistent configuration settings with device625). In FIG. 8C, device 650 is not paired with device 600. As describedbelow, device 600 can establish a temporary connection with device 650to share audio data with another user (e.g., Chance) that is also beingprovided to paired device 625 (e.g., Taylor's own earbuds), but device650 does not remain associated with device 600 after the temporaryconnection ends.

FIG. 6C shows proximity condition range indicator 605 around device 600.A proximity condition range indicator is also referred to herein as a“proximity zone indicator” or simply as a “proximity zone.” Device 650is not inside of proximity condition range indicator 605. Proximitycondition range indicator 605 is included as a visual aid, and isintended to represent a physical proximity that would satisfy aproximity condition. For example, range indicator 605 can represent therange of a near-field communication detection circuitry of device 600.In some embodiments, any appropriate technique can be used to detectproximity between devices. For instance, in some examples, wide-bandwireless connection is used. Wide-band wireless connection is used, forexample, to determine one or more of: directionality, distance, andorientation, of one or more devices. Thus, presence of a detectabledevice within (e.g., partially or completely) proximity condition rangeindicator 605 would satisfy a proximity condition, but would not if thedetectable device is located outside of the range indicator 605. One ofskill would appreciate that a detection range of physical proximity canbe non-uniform, can be affected by numerous variables (e.g., wirelessinterference, air humidity, or the like), and can include points inspace in three dimensions, all of which are intended to be within thescope of this disclosure. Thus, the graphical representation ofproximity condition range indicator 605 is not intended to limit thescope of determining whether a proximity condition is satisfied.Furthermore, the figures are not necessarily to scale and are includedmerely as a visual aid. Thus, unless otherwise noted, the size and scaleof features depicted in the figures are not intended as a limitation ona distance required to be in close proximity or to satisfy a proximitycondition. In some embodiments, in response to detecting input 610 a,device 600 enters a mode in which device 600 is configured to detectdevices within proximity condition range indicator 605 with which audiodata can be shared.

FIG. 6D illustrates an exemplary view of a scenario that includes device600 at a short distance away from device 600. As shown in 6D, device 600and device 650 are close together, and now device 650 is at leastpartially within the proximity condition range indicator 605. Sinceproximity condition range indicator 605 represents a physical proximitythat satisfies the proximity condition, device 600 detects an indicationthat a physical proximity between the device 600 and device 650satisfies the proximity condition (e.g., and, in response, initiatescommunication with device 650, for example, to send an indication thatthe condition is satisfied). In some examples, device 650 detects anindication that the proximity condition is satisfied (e.g., and, inresponse, initiates communication with device 600, for example, to sendan indication that the condition is satisfied).

In response to detecting the indication that the physical proximitysatisfies the proximity condition, device 600 displays user interface608 indicating that the physical proximity between device 600 and thedevice 650 satisfies the proximity condition, as shown in FIG. 6D. Userinterface 608 includes proximity user interface 608 a, which identifiesthe device that satisfied the proximity condition with device 600 andprovides confirmation affordance 608 a-3 that, when selected, continuesthe process of sharing audio data by initiating a connection (e.g.,communication link) with device 650 for providing audio data, whileconcurrently providing audio data to device 625. Proximity userinterface 608 a identifies device 650 as being within proximitycondition range indicator 605 with text indicator 608 a-1 (“Chance'sEarbuds”) and graphical element 608 a-2, which includes a representativeimage of device 650. Graphical element 608 a-2 indicates that device 650is a pair of wireless earbuds (as opposed to, e.g., a pair of wirelessheadphones, as depicted by graphical element 606 a-3 in FIG. 6C).

In FIG. 6D, device 600 detects input 610 b (e.g., a tap) correspondingto selection of confirmation affordance 608 a-3. In response todetecting input 610 b, device 600 displays user interface 612, as shownin FIG. 6E. User interface 612 includes connection instructions userinterface 612 a, which includes text indicator 612 a-1 (e.g., 608 a-1),graphical element 612 a-2, and instructions 612 a-3 for continuing theprocess of connecting device 650 with device 600. Instructions 612 a-3direct a user to press and hold button 650 c-1 on device 650, andgraphical element 612 a-2 includes a representative image of device 650from a perspective in which a representation of button 650 c-1 can beseen.

In FIG. 6E, device 650 detects input 610 c, which includes a press andhold of button 650 c-1. In some embodiments, in response to detectinginput 610 c, device 650 sends a signal to device 600 indicating thatdevice 650 can be connected to device 600. After (e.g., in response to)receiving the signal from device 650, device 600 displays user interface614, as shown in FIG. 6F. User interface 614 indicates that device 600is in the process of creating communication link C2 with device 650.User interface 614 includes connecting user interface 614 a, whichincludes text indicator 614 a-1 (e.g., 608 a-1), graphical element 614a-2 (e.g., a representative image of device 650 from a differentperspective than graphical element 608 a-3 and graphical element 612a-3). In some embodiments, device 600 connects to a second externaldevice (e.g., device 650) and displays user interface 614 in response todetecting input 610 b (e.g., without requiring input 610 c on device 650and without displaying user interface 612).

After (e.g., in response to) establishing communication link C2 withdevice 600 displays user interface 616, as shown in FIG. 6G. In FIG. 6G,device 600 is concurrently connected to and providing audio data todevice 625 (via communication link C1) and device 650 (via communicationlink C2) such that device 625 and device 650 output the same audio. Insome embodiments, device 600 connects to a second external device (e.g.,device 650) and displays user interface 616 in response to detectinginput 610 b (e.g., without requiring input 610 c on device 650 andwithout displaying user interfaces 612 and 614).

User interface 616 includes audio media user interface 616 a (e.g., anupdated version of audio media user interface 604 a) indicating thatdevice 600 is concurrently providing audio data to device 625 and device650. Audio media user interface 616 a includes current audio indicator616 a-1, which includes track name (Track 1) and artist name (DJAppleseed). Compared to current audio indicator 604 a-1, current audioindicator 616 a-1 indicates that audio is being provided to twoheadphones, instead of only device 625 (Taylor's Earbuds) as in FIG. 6A.Audio media user interface 616 a includes affordances 616 a-2, 616 a-3,616 a-4, 616 a-5, and 616 a-6. The check marks on affordance 616 a-3 andaffordance 616 a-4 indicate that device 625 (“Taylor's Earbuds”) anddevice 650 are currently selected for audio output, consistent withcurrent audio indicator 616 a-1. Affordance 616 a-3 and affordance 616a-4 each include a volume slider that, when selected, controls theindividual volume level of the corresponding device (e.g., the volumeslider on affordance 616 a-4 can be selected to adjust the volume levelof device 650 without changing the volume level for device 625).Affordance 616 a-2 can be selected to output audio data on a bedroomspeaker associated with device 600 (e.g., and to cease providing audiodata to device 625 and device 650). Volume affordance 616 a-6 can beselected to adjust the volume levels for device 625 and device 650 witha single input. In some embodiments, adjusting the volume level fordevice 625 and device 650 with affordance 616 a-6 sets the volume levelsfor device 625 and device 650 to the same volume level (e.g., even ifdevice 625 and device 650 had different volume levels prior to selectionof affordance 616 a-6). In some embodiments, adjusting the volume levelfor device 625 and device 650 with affordance 616 a-6 sets the volumelevels for device 625 and device 650 to respective volume levels basedon the initial volume level of the respective device and the input onaffordance 616 a-6 (e.g., the position to which volume adjustmentaffordance 616 a-7 is moved from its initial position).

In FIG. 6G, earbuds 650 a and 650 b of device 650 are depicted withoutcase 650 c and outside of proximity condition range indicator 605. Insome embodiments, earbuds 650 a and 650 b must be in case 650 c toestablish communication link C2 (e.g., during input 610 c), and canreceive audio data from device 600 without case 650 c aftercommunication line C2 is established. In some embodiments, device 650does not include case 650 c and/or earbuds 650 a and 650 b do not needto be in case 650 c to establish communication link C2 with device 600.

As mentioned, in FIG. 6G, device 650 is outside of proximity conditionrange indicator 605, while maintaining communication link C2 (e.g.,device 650 does not need to remain inside of proximity condition rangeindicator 605 to receive audio data). In FIG. 6H (e.g., after device 650is moved away from device 600 and outside of proximity condition rangeindicator 605), device 650 is positioned inside of proximity conditionrange indicator 615 (e.g., device 650 is moved back towards device 600).In some embodiments, proximity condition range indicator 615 is the sameas proximity condition range indicator 605. In some embodiments,proximity condition range indicator 615 is different from proximitycondition range indicator 605. Proximity condition range indicator 615represents a physical proximity that satisfies a disconnect proximitycondition. In some embodiments, the disconnect proximity condition isthe same as the proximity condition described above for initiating theprocess for providing audio data with a second external device. In someembodiments, the disconnect proximity condition is different from theproximity condition for initiating the process for providing audio datawith a second external device.

Since proximity condition range indicator 615 represents a physicalproximity that satisfies the disconnect proximity condition, device 600detects an indication that a physical proximity between the device 600and device 650 satisfies the disconnect proximity condition (e.g., and,in response, initiates communication with device 650, for example, tosend an indication that the disconnect condition is satisfied). In someexamples, device 650 detects an indication that the disconnect proximitycondition is satisfied (e.g., and, in response, initiates communicationwith device 600, for example, to send an indication that the disconnectcondition is satisfied).

In response to detecting the indication that the physical proximitysatisfies the disconnect proximity condition, device 600 displays userinterface 618 indicating that the physical proximity between device 600and the device 650 satisfies the disconnect proximity condition. Userinterface 618 includes disconnect user interface 618 a, which identifiesthe device (e.g., device 650) that satisfied the disconnect proximitycondition with device 600 and provides disconnect affordance 618 a-4that, when selected, initiates a process for disconnecting from device600 the device that is in proximity with device 600. Disconnectproximity user interface 618 a identifies device 650 as being withinproximity condition range indicator 615 with text indicator 618 a-1(“Chance's Earbuds”) and includes graphical element 618 a-2 andgraphical element 618 a-3, graphical element 618 a-2 indicates thatdevice 600 is temporarily sharing audio with the device represented bygraphical element 618 a-3, which includes a representative image ofdevice 650.

In some embodiments, device 600 displays disconnect user interface 618 ain accordance with a determination that the device that satisfies thedisconnect proximity condition with device 600 is not paired with device600. In some embodiments, if device 600 determines that the device thatsatisfies the disconnect proximity condition with device 600 is pairedwith device 600, device 600 foregoes displaying disconnect userinterface 618 a and optionally displays a different user interface. Forexample, in some embodiments, in which device 625 is paired with device600, in accordance with a determination that device 625 satisfies thedisconnect proximity condition with device 600, device 600 displaysinformation about device 625 (e.g., a current state of device 625, suchas battery level) without an option to disconnect device 625 from device600 or cease providing audio data to device 625.

In FIG. 6H, device 600 detects input 610 d (e.g., a tap) correspondingto selection of disconnect affordance 618 a-4. In response to detectinginput 610 d, device 600 ceases providing audio data to device 650. Insome embodiments, in response to detecting input 610 d, device 600disconnects from device 650 (e.g., disconnects communication link C2)and displays user interface 620 (e.g., user interface 618 withoutdisconnect user interface 618 a), as shown in FIG. 6I. In someembodiments, device 600 continues to provide audio data to device 625after ceasing to provide audio data with device 650 and/or disconnectingfrom device 650.

In FIG. 6I, after device 600 is disconnected from device 650, device 600remains connected with device 625, and device 650 is positioned outsideof proximity condition range indicator 635. In FIG. 6J, device 650 ispositioned inside of proximity condition range indicator 635 (e.g.,device 650 is moved back towards device 600). In some embodiments,proximity condition range indicator 635 is the same as proximitycondition range indicator 605 and/or 615. In some embodiments, proximitycondition range indicator 635 is different from proximity conditionrange indicator 605 and/or 615. Proximity condition range indicator 635represents a physical proximity that satisfies a second proximitycondition. In some embodiments, the second proximity condition is thesame as the proximity condition described above for initiating theprocess for providing audio data with a second external device. In someembodiments, the second proximity condition is different from theproximity condition for initiating the process for providing audio datawith a second external device.

Since proximity condition range indicator 635 represents a physicalproximity that satisfies the second proximity condition, device 600detects an indication that a physical proximity between the device 600and device 650 satisfies the second proximity condition (e.g., and, inresponse, initiates communication with device 650, for example, to sendan indication that the second condition is satisfied). In someembodiments, device 650 detects an indication that the second proximitycondition is satisfied (e.g., and, in response, initiates communicationwith device 600, for example, to send an indication that the secondcondition is satisfied). In some embodiments, device 600 detects theindication that the physical proximity between the device 600 and device650 satisfies the second proximity condition without having previouslydetected an input corresponding to selection of share audio affordance604 a-1.

In response to detecting the indication that the physical proximitysatisfies the second proximity condition, device 600 displays userinterface 622 indicating that the physical proximity between device 600and the device 650 satisfies the second proximity condition. Userinterface 622 includes second proximity user interface 622 a, whichidentifies the device that satisfied the second proximity condition withdevice 600 and provides share audio affordance 622 a-4 that, whenselected, initiates the process of establishing a connection with device650 to provide audio data concurrently with device 625 and device 650.In some embodiments, device 600 does not have to have previouslyestablished a connection or communication link with device 650 in orderto display second proximity user interface 622 a.

Second proximity user interface 622 a identifies device 650 as beingwithin proximity condition range indicator 635 with text indicator 622a-1 (“Chance's Earbuds”), graphical element 622 a-2, and graphicalelement 622 a-3. Graphical element 622 a-2 includes information (e.g.,text) that device 600 can temporarily share audio with device 650.Graphical element 622 a-3 includes a representative image of device 650.In addition, second proximity user interface 622 a includes affordance622 a-5 that, when selected, connects (e.g., pairs) device 650 to device600. In some embodiments, in contrast to temporarily sharing audio byselecting share affordance 622 a-4, connecting device 650 to device 600by selecting affordance 622 a-5 disconnects communication link C1between device 625 and device 600, such that device 600 does notconcurrently provide audio data to both device 625 and device 650 (e.g.,device 650 replaces device 625 as the primary headphone device).

In FIG. 6J, device 600 detects input 610 e (e.g., a tap) correspondingto selection of share affordance 622 a-4. In response to detecting input610 e, device 600, initiates the process of establishing a connectionwith device 650 to provide audio data concurrently to device 625 anddevice 650 (e.g., including the process described with reference toFIGS. 6E-6F).

In some embodiments, after device 600 has established communication linkC2 with device 650, device 600 displays user interface 624, includingconfirmation user interface 624 a, as shown in FIG. 6K. Confirmationuser interface 624 a indicates (e.g., via graphical elements 624 a-1,624 a-2, and 624 a-3) that device 600 is sharing (or configured toshare) audio data with device 650, while concurrently providing audiodata to device 625. In some embodiments, confirmation user interface 624a is displayed upon establishing a communication link between device 600and device 650 in response to input 610 b or input 610 c, or afterdisplaying connecting user interface 614 a.

In FIG. 6K, device 600 detects input 610 f (e.g., a tap) correspondingto selection of done affordance 624 a-4. In response to detecting input610 f, device 600 ceases displaying confirmation user interface 624 a,while maintaining communication links C1 and C2.

Turning now to FIG. 6L, a scenario is depicted in which device 600displays user interface 604 (described above) and is connected (e.g.,via communication link C1) with device 625 (“Taylor's Earbuds”). Device650 is connected (via communication link C3) to device 675 (e.g., aphone associated with the same user as device 650). Device 675 is withinproximity condition range indicator 635, and neither device 650 nordevice 675 is connected to device 600. In some embodiments, in contrastto device 650 being within proximity condition range indicator 635 inFIG. 6J, device 600 does not display a proximity user interface (e.g.,622 a) for sharing audio data with device 675. For example, device 600foregoes displaying a proximity user interface identifying device 675 inaccordance with a determination that device 675 is a particular type ofdevice (e.g., a phone) or that device 675 is not a particular type ofdevice (e.g., wireless headphones or wireless earbuds).

In FIG. 6L, device 600 detects input 610 g (e.g., a tap) correspondingto selection of share audio affordance 604 a-4. In response to detectinginput 610 g, device 600 initiates the process to provide audio dataconcurrently with device 625 and a second external device (e.g., theprocess described with reference to FIG. 6A). In some embodiments, inresponse to detecting selection of share audio affordance 604 a-4,device 600 enters a mode in which device 600 will share audio data withdevice 675, while concurrently providing audio data to device 625 (e.g.,device 600 applies a proximity condition in response to selection ofaudio share affordance 604 a-4 that is different from a proximitycondition applied prior to selection of audio share affordance 604 a-4).

In FIG. 6M, device 675 is within proximity condition range indicator605. In some embodiments, proximity condition range indicator 635applies prior to selection of share audio affordance 604 a-4 andproximity condition range indicator 605 applies after selection of shareaudio affordance 604 a-4 (e.g., for a predetermined amount of time).Since proximity condition range indicator 605 represents a physicalproximity that satisfies the proximity condition, device 600 detects anindication that a physical proximity between device 600 and device 675satisfies the proximity condition (e.g., and, in response, initiatescommunication with device 675, for example, to send an indication thatthe condition is satisfied). In some embodiments, device 675 detects anindication that the proximity condition is satisfied (e.g., and, inresponse, initiates communication with device 600, for example, to sendan indication that the condition is satisfied).

In response to detecting the indication that the physical proximitysatisfies the proximity condition, device 600 displays user interface626 indicating that the physical proximity between device 600 and thedevice 675 satisfies the proximity condition, as shown in FIG. 6M. Userinterface 626 includes proximity user interface 626 a, which identifiesthe user (e.g., Chance) of the device (e.g., 675) that satisfied theproximity condition with device 600. Proximity user interface 626 aprovides, inter alia, confirmation affordance 626 a-3 that, whenselected, continues the process of sharing audio data by initiating aconnection (e.g., communication link) with device 675 for providingaudio data, while concurrently providing audio data to device 625.Proximity user interface 626 a identifies device 675 as being withinproximity condition range indicator 605 with text indicator 626 a-1,which indicates the action performed by selecting share audio affordance626 a-3, and includes graphical element 626 a-2, which providesinformation that device 600 can be used independently to control thevolume of device 625 while sharing audio data with device 675. In someembodiments, user interface 626 a is displayed in accordance with adetermination that the proximity of device 675 with device 600 satisfiesthe proximity condition (e.g., instead of the proximity of device 650).In some embodiments, in response to detecting the indication that thephysical proximity between device 600 and device 675 satisfies theproximity condition, device 600 displays a proximity user interfacesimilar to proximity user interface 608 a, except with information andgraphical elements corresponding to device 675 instead of device 650.

In FIG. 6M, device 600 detects input 610 h (e.g., a tap) correspondingto selection of share affordance 626 a-3. In response to detecting input610 h, device 600 initiates communication link C4 with device 675 toprovide audio data concurrently to device 625 and device 650 (viacommunication link C3 between device 675 and device 650), as shown inFIG. 6N.

In the embodiment illustrated in FIG. 6N, device 600 displays userinterface 628 while concurrently providing audio data to device 625 anddevice 650 (via device 675). User interface 628 includes audio mediauser interface 628 a, which indicates (via audio information 628 a-1)that audio data is being provided concurrently to two headphones. Audiomedia user interface 628 a includes affordance 628 a-2 that, whenselected, displays user interface 630, including audio media userinterface 630 a (e.g., audio media user interface 616 a), as shown inFIG. 6O. Audio media user interface 630 a includes affordance 630 a-1that, when selected (e.g., via input 610 j), displays audio applicationuser interface 632 a, as shown in FIG. 6P. Audio application userinterface 632 a includes, inter alia, track controls 632 a-1, indication632 a-2 that audio data is being concurrently provided to twoheadphones, and volume control affordance 632 a-3. In FIG. 6P, device600 detects input 610 k (e.g., a tap) corresponding to selection ofvolume control affordance 632 a-3. In response to detecting input 610 k,device 600 displays user interface 634, including audio media userinterface 634 a, as shown in FIG. 6Q. Audio media user interface 634 ais the same as audio media user interface 632 a, except that trackcontrols 632 a-1 are replaced with individual volume control affordances634 a-1 and 634 a-2 corresponding to device 625 and device 650,respectively. Volume control affordance 634 a-2 corresponding to device650 includes disconnect affordance 634 a-3 that, when selected, causesdevice 600 to cease sharing audio data with device 650, e.g., bydisconnecting communication link C4 between device 600 and device 675.In some embodiments, device 600 displays user interface 634 a, includingdisconnect affordance 634 a-3, while device 650 is connected directly todevice 600 (e.g., via communication link C2, as shown in FIG. 6G), anddisconnects from device 650 in response to selection of disconnectaffordance 634 a-3.

Turning to FIG. 6R, device 600 displays an exemplary user interface forceasing to share audio data with a second external device whileconcurrently providing audio data with device 625. In FIG. 6R, device600 is connected to device 625 and device 650 (via device 675). In someembodiments, device 650 is connected directly to device 600. Whiledevice 600 is configured to concurrently provide audio data to bothdevice 625 and device 650, device 600 displays settings user interface636 (e.g., a Bluetooth settings menu). Settings user interface 636includes graphical element 636-1 and disconnect affordance 636-2.Graphical element 636-1 indicates that device 600 is sharing audio withdevice 650 (Chance's Earbuds). Disconnect affordance 636-2, whenselected, causes device 600 to cease sharing audio data with device 650,e.g., by disconnecting communication link C4 between device 600 anddevice 675. In embodiments in which device 600 displays user interface636 while device 650 is connected directly to device 600 (e.g., viacommunication link C2, as shown in FIG. 6G), device 600 disconnects fromdevice 650 in response to selection of disconnect affordance 636-2.

FIG. 7 is a flow diagram illustrating a method for sharing audio datausing an electronic device in accordance with some embodiments. Method700 is performed at a device (e.g., 100, 300, 500, or 600) with adisplay device (e.g., 602). Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for sharingaudio data. The method reduces the cognitive burden on a user forsharing audio data, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toshare audio data faster and more efficiently conserves power andincreases the time between battery charges.

While the electronic device (e.g., 600) is connected to a first externaldevice (e.g., 625; wireless headphones or wireless earbuds) via acommunication link (e.g., C1; Bluetooth), where the electronic device isconfigured to provide audio data to the first external device via thecommunication link, the electronic device displays (702), via thedisplay device, a first user interface (e.g., 604) including a firstaffordance (e.g., 604-4). In some embodiments, the electronic devicedisplays the first affordance concurrently with an indication that theelectronic device is connected to the first external device. In someembodiments, the electronic device displays the first affordance inaccordance with a determination that the electronic device is connectedto the first external device and, optionally, that the electronic deviceis running an audio media application or actively providing audio datato the first external device via the communication link. In someembodiments, an external device is a single physical device, such as apair of headphones with two ear cups or earbuds that are physicallyconnected via, e.g., a wire or headband. In some embodiments, anexternal device is a compound device with multiple, physically separatecomponents or physical units that operate together as one device. Insome embodiments, a compound device has a primary component (e.g.,earbud) that connects with the electronic device and a secondarycomponent that communicates with the primary component and receivesaudio signals from the electronic device via the primary component. Insome embodiments, a compound device includes two components that areeach connected to the electronic device, but are treated by theelectronic device as a single external device.

In some embodiments, the electronic device displays the first userinterface including the first affordance in accordance with adetermination that the first external device is configured to receiveaudio data from the electronic device while the electronic device isconcurrently providing audio data to the second external device. In someembodiments, in accordance with a determination that the first externaldevice is not configured to receive audio data from the electronicdevice while the electronic device is concurrently providing audio datato the second external device, the electronic device displays the firstuser interface without the first affordance.

In some embodiments, the electronic device displays the first userinterface including the first affordance in accordance with adetermination that the electronic device is running an audio mediaapplication (e.g., a music application, a podcast application, an audiobook application, a multimedia application, a web browser playing audioand/or video). In some embodiments, in accordance with a determinationthat the electronic device is not running an audio media application,the electronic device displays the first user interface without thefirst affordance.

The electronic device detects (704) an input (e.g., 610 a) correspondingto selection of the first affordance.

In response to detecting the input corresponding to selection of thefirst affordance, the electronic device initiates (706) a process toprovide audio data concurrently with the first external device (e.g.,625) and a second external device (e.g., 650, 675; wireless headphonesor wireless ear pods) different from the first external device. In someembodiments, the electronic device displays a visual indication that theelectronic device has initiated a process to share audio dataconcurrently with the first external device and a second externaldevice. In some embodiments, the process to share audio data includesdisplaying a user interface with instructions to bring another deviceclose to the electronic device to temporarily share audio. Displaying avisual indication that the electronic device has initiated a process toshare audio data concurrently with the first external device and asecond external device and displaying a user interface with instructionsto bring another device close to the electronic device to temporarilyshare audio provides feedback to a user that the electronic device isprepared to share audio data and informs the user how to continue theaudio sharing process. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

After initiating the process to provide audio data concurrently to thefirst external device and a second external device, the electronicdevice detects (708) an indication that a physical proximity between theelectronic device and the second external device satisfies a proximitycondition (e.g., represented by 605). In some embodiments, theindication is detected using a near-field communication technique. Insome embodiments, the proximity condition is satisfied if the secondelectronic device is no farther than a threshold distance away from theelectronic device. In some embodiments, the threshold distance is 6inches, 12 inches, or 18 inches.

In response to detecting the indication that the physical proximitybetween the electronic device and the second external device satisfiesthe proximity condition, the electronic device displays (710) a seconduser interface (e.g., 608, 608 a) indicating that the physical proximitybetween the electronic device and the second external device satisfiesthe proximity condition. Displaying the second user interface indicatingthat the physical proximity between the electronic device and the secondexternal device satisfies the proximity condition automatically providesfeedback by indicating to the user that the physical proximity satisfiesthe proximity condition, thus reducing the number of inputs needed toshare audio data. Providing improved feedback, reducing the number ofinputs needed to perform an operation, and performing an operation whena set of conditions has been met without requiring further user inputenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the second user interface includes instructions forcompleting the process to share audio data concurrently with the firstexternal device and the second external device. In some embodiments, theprocess to share audio data concurrently with the first external deviceand the second external device includes establishing a temporaryconnection between the electronic device and the second external device.In some embodiments, second user interface includes an indication theelectronic device has established, or is in the process of establishing,a connection with the second electronic device to share audio data withthe second external device concurrently with the first device.

In some embodiments, the second external device is configured to outputaudio based on the audio data from the electronic device and isconnected directly to the electronic device (e.g., FIG. 6G, 6K). Forexample, in some embodiments, the second external device does notreceive audio data from the electronic device via an intermediatedevice, such as a phone, to which the second external device isconnected.

In some embodiments, the second external device (e.g., 675) is connectedto a third external device (e.g., 650; wireless headphones or wirelessearbuds) and is configured to provide the audio data from the electronicdevice to the third external device.

In some embodiments, as part of initiating a process to provide audiodata concurrently with the first external device and a second externaldevice, the electronic device displays a representation (e.g., 606 a-2)of a first potential second external device. In some embodiments, aspart of initiating a process to provide audio data concurrently with thefirst external device and a second external device, the electronicdevice displays a representation (e.g., 606 a-3) of a second potentialsecond external device. In some embodiments, the electronic devicedisplays images of audio output devices that are configured to connectto the electronic device and receive audio data from the electronicdevice while the electronic device concurrently provides audio data tothe first external device. In some embodiments, the electronic devicesequentially displays the representation of the first potential secondexternal device followed by the representation of the second potentialsecond external device (e.g., the electronic device cycles throughrepresentations of potential second external devices). Displaying arepresentation of one or more external devices with which the electronicdevice can share data provides feedback by indicating to the user whichdevice(s) can be used to share data. Since not all devices supportsharing capability, displaying potential options helps the user knowwhich devices can be used. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the second user interface includes a secondaffordance (e.g., 608 a-3) that, when selected, causes the electronicdevice to provide audio data concurrently with the first external deviceand a second external device. In some embodiments, although theelectronic device initiates the process to provide audio dataconcurrently with the first external device and a second external devicein response to detecting the input corresponding to selection of thefirst affordance, the electronic device does not actually provide theaudio data until the second affordance is selected. Causing theelectronic device to provide audio data concurrently with the firstexternal device and a second external device in response to selection ofa second affordance on the second user interface provides improvedcontrol by confirming that sharing is truly desired and avoidsinadvertently sharing audio data before intended or with an unintendeddevice. Providing improved control over the sharing process enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, after detecting the indication that the physicalproximity between the electronic device and the second external devicesatisfies the proximity condition and before providing audio dataconcurrently with the first external device and the second externaldevice, the electronic device displays instructions (e.g., 612 a-3) toprovide an input at the second external device. In some embodiments, thesecond external device requires an input (e.g., a press of a hardwarebutton on the second external device) to connect to the electronicdevice.

In some embodiments, the electronic device receives an indication thatthe second external device is connected to the electronic device. Insome embodiments, in response to receiving the indication that thesecond external device is connected to the electronic device, theelectronic device provides an indication that the second external deviceis connected to the electronic device (e.g., 608 a, 616 a-4, 624 a). Insome embodiments, providing the indication that the second externaldevice is connected to the electronic device includes displaying agraphical representation of the second external device. In someembodiments, the indication that the second external device is connectedto the electronic device includes an audio output and/or a tactileoutput.

In some embodiments, while the second external device is connected tothe electronic device, the electronic device displays a third affordance(e.g., 618 a-4, 634 a-3, 636-2, 906-3) that, when selected, disconnectsthe second external device from the electronic device.

In some embodiments, while the second external device is connected tothe electronic device, the electronic device detects an indication thatthe physical proximity between the electronic device and the secondexternal device satisfies a second proximity condition (e.g.,represented by 615). In some embodiments, the electronic device displaysthe third affordance (e.g., 618 a-4) in response to detecting theindication that the physical proximity between the electronic device andthe second external device satisfies the second proximity condition. Insome embodiments, the third affordance is displayed in accordance with adetermination that the second external device has re-entered a rangerequired to satisfy the proximity condition. In some embodiments, thesecond proximity condition is the same as the (first) proximitycondition. Displaying an affordance for disconnecting the secondexternal device in response to detecting an indication that the physicalproximity between the electronic device and the second external devicesatisfies a second proximity condition provides feedback that the usercan cease sharing audio with the second external device andautomatically presents the option to disconnect the second externaldevice, thus reducing the number of inputs needed to cease sharing audiodata. Providing improved feedback, reducing the number of inputs neededto perform an operation, and performing an operation when a set ofconditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the electronic device displays the third affordancein accordance with a determination that the second external device isnot paired with the electronic device. In some embodiments, two devices(e.g., the second external device and the electronic device) are pairedif they have a persistent association with each other and are configuredto exchange data via a communication link. In some embodiments, devicesare not paired if they do not have a persistent association with eachother. In some embodiments, paired devices remain associated with eachother when a communication link between the devices is not currentlyactive, whereas devices that are temporarily connected but not pairedare not associated with each other after the temporary connection ends.In some embodiments, paired devices share common configuration settings.In some embodiments, if the second external device is paired with theelectronic device, the electronic device foregoes display of the thirdaffordance and, optionally, displays information (e.g., battery level)of the second external device.

In some embodiments, the third affordance is displayed in a menu userinterface (e.g., 636). In some embodiments, the menu user interface is aBluetooth settings menu or an audio output menu user interface of anaudio media player application.

Note that details of the processes described above with respect tomethod 700 (e.g., FIG. 7) are also applicable in an analogous manner tothe methods described below. For example, method 800, 1000, and/or 1200optionally includes one or more of the characteristics of the variousmethods described above with reference to method 700. For example,operation 710 displaying the second user interface in method 700 can beperformed in response to detecting the indication in operation 802 ofmethod 800. As another example, the operations of method 700 can beperformed prior to the operations of method 1000 and/or method 1200. Forbrevity, these details are not repeated below.

FIG. 8 is a flow diagram illustrating a method for sharing audio datausing an electronic device in accordance with some embodiments. Method800 is performed at a device (e.g., 100, 300, 500, or 600) with adisplay device (e.g., 602). Some operations in method 800 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 800 provides an intuitive way for sharingaudio data. The method reduces the cognitive burden on a user forsharing audio data, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toshare audio data faster and more efficiently conserves power andincreases the time between battery charges.

While the electronic device is connected to a first external device(e.g., 625; wireless headphones or wireless ear pods) via acommunication link (e.g., C1), where the electronic device is configuredto provide audio data to the first external device via the communicationlink (e.g., and not currently configured to provide audio data to asecond external device (e.g., 650)), the electronic device detects (802)an indication that a physical proximity between the electronic deviceand a second external device (e.g., 650; wireless headphones or wirelessear pods), different from the first external device, satisfies aproximity condition (e.g., represented by 635). In some embodiments, theindication is detected using a near-field communication technique. Insome embodiments, the proximity condition is satisfied if the secondelectronic device is no farther than a threshold distance away from theelectronic device. In some embodiments, the threshold distance is 6inches, 12 inches, or 18 inches.

In response to detecting the indication that the physical proximitybetween the electronic device and the second external device satisfiesthe proximity condition, the electronic device displays (804), via thedisplay device, a first user interface (e.g., 622, 622 a) including afirst affordance (e.g., 622 a-5).

In some embodiments, the first user interface includes an indicationthat the electronic device can temporarily share audio data with thesecond external device. In some embodiments, the first user interfaceincludes an indication (e.g., on the first affordance) that selectingthe first affordance will cause the electronic device to share audiodata with the second external device. In some embodiments, theelectronic device displays the first affordance in accordance with adetermination that the electronic device is connected to the firstexternal device and, optionally, that the electronic device is runningan audio media application or actively providing audio data to the firstexternal device via the communication link. Displaying the first userinterface with the first affordance for sharing audio data in responseto detecting the indication that the physical proximity between theelectronic device and the second external device satisfies the proximitycondition automatically provides feedback by indicating to the user thatthe physical proximity satisfies the proximity condition and that audiodata can be shared, thus reducing the number of inputs needed to shareaudio data. Providing improved feedback, reducing the number of inputsneeded to perform an operation, and performing an operation when a setof conditions has been met without requiring further user input enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

The electronic device detects (806) an input (e.g., 610 e) correspondingto selection of the first affordance.

In response to detecting the input corresponding to selection of thefirst affordance, the electronic device initiates (808) a process toprovide audio data concurrently with the first external device (e.g.,625) and the second external device (e.g., 650). In some embodiments,the process to share audio data concurrently with the first externaldevice and the second external device includes establishing a temporaryconnection between the electronic device and the second external device.In some embodiments, the process to share audio data concurrently withthe first external device and the second external device includesdisplaying a visual indication that the electronic device hasestablished, or is in the process of establishing, a connection with thesecond external device to share audio data concurrently with the firstexternal device and a second external device. In some embodiments, theprocess to share audio data concurrently with the first external deviceand the second external device includes displaying instructions forcompleting the process to share audio data concurrently with the firstexternal device and the second external device. Displaying instructionsfor completing the process to share audio data provides feedback to auser that the electronic device is prepared to share audio data andinforms the user how to continue the audio sharing process. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device displays the first userinterface including the first affordance in accordance with adetermination that the first external device is configured to receiveaudio data from the electronic device while the electronic device isconcurrently providing audio data to the second external device. In someembodiments, in accordance with a determination that the first externaldevice is not configured to receive audio data from the electronicdevice while the electronic device is concurrently providing audio datato the second external device, the electronic device foregoes displayingthe first user interface.

In some embodiments, the electronic device displays the first userinterface including the first affordance in accordance with adetermination that the electronic device is running an audio mediaapplication (e.g., a music application, a podcast application, an audiobook application, a multimedia application, a web browser playing audioand/or video). In some embodiments, in accordance with a determinationthat the electronic device is not running an audio media application,the electronic device foregoes displaying the first user interface.

In some embodiments, the electronic device displays the first userinterface including the first affordance in accordance with adetermination that the second external device is not paired with theelectronic device. In some embodiments, two devices (e.g., the secondexternal device and the electronic device) are paired if they have apersistent association with each other and are configured to exchangedata via a communication link. In some embodiments, devices are notpaired if they do not have a persistent association with each other. Insome embodiments, paired devices remain associated with each other whena communication link between the devices is not currently active,whereas devices that are temporarily connected but not paired are notassociated with each other after the temporary connection ends. In someembodiments, paired devices share common configuration settings. In someembodiments, if the second external device is paired with the electronicdevice, the electronic device foregoes displaying the first userinterface and, optionally, displays information (e.g., battery level) ofthe second external device.

In some embodiments, the first user interface includes a secondaffordance (e.g., 622 a-5) that, when selected, pairs the secondexternal device with the electronic device. In some embodiments, pairingthe second external device with the electronic device creates apersistent association between the second external device and theelectronic device. In some embodiments, a second affordance, whenselected, disconnects the first external device from the electronicdevice. Displaying an affordance to pair the second external device(e.g., in addition to concurrently displaying an affordance fortemporarily sharing data with the second external device) in response todetecting the indication that the physical proximity between theelectronic device and the second external device satisfies the proximitycondition provides feedback that a user has the option of either pairingor temporarily sharing audio data with the second external device, andautomatically presents those options. Providing improved visual feedbackto the user and performing an operation (e.g., displaying the pairingand sharing options) when a set of conditions has been met withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the second external device is configured to outputaudio based on the audio data from the electronic device and iswirelessly connected directly to the electronic device (e.g., FIG. 6K).For example, in some embodiments, the second external device does notreceive audio data from the electronic device via an intermediatedevice, such as a phone, to which the second external device isconnected.

In some embodiments, after detecting the input corresponding toselection of the first affordance and before providing audio dataconcurrently with the first external device and the second externaldevice, the electronic device displays instructions (e.g., 612 a-3) toprovide an input at the second external device. In some embodiments, thesecond external device requires an input (e.g., a press (e.g., 610 c) ofa hardware button on the second external device) to connect to theelectronic device.

In some embodiments, the electronic device receives an indication thatthe second external device is connected to the electronic device. Insome embodiments, in response to receiving the indication that thesecond external device is connected to the electronic device, theelectronic device provides an indication (e.g., 616 a-4, 624 a) that thesecond external device is connected to the electronic device. In someembodiments, providing the indication that the second external device isconnected to the electronic device includes displaying a graphicalrepresentation of the second external device. In some embodiments, theindication that the second external device is connected to theelectronic device includes an audio output and/or a tactile output.

In some embodiments, while the second external device is connected tothe electronic device, the electronic device displays a secondaffordance (e.g., 618 a-4, 634 a-3, 636-2, 906-3) that, when selected,disconnects the second external device from the electronic device. Insome embodiments, while the second external device is connected to theelectronic device, the electronic device detects an indication that thephysical proximity between the electronic device and the second externaldevice satisfies a second proximity condition (e.g., FIG. 6H). In someembodiments, the electronic device displays the second affordance inresponse to detecting the indication that the physical proximity betweenthe electronic device and the second external device satisfies thesecond proximity condition. In some embodiments, the second affordanceis displayed in accordance with a determination that the second externaldevice has re-entered a range required to satisfy the proximitycondition (e.g., the second proximity condition or the (first) proximitycondition. In some embodiments, the second proximity condition is thesame as the (first) proximity condition. Displaying an affordance fordisconnecting the second external device in response to detecting anindication that the physical proximity between the electronic device andthe second external device satisfies a second proximity conditionprovides feedback that the user can cease sharing audio with the secondexternal device and automatically presents the option to disconnect thesecond external device, thus reducing the number of inputs needed tocease sharing audio data. Providing improved feedback, reducing thenumber of inputs needed to perform an operation, and performing anoperation when a set of conditions has been met without requiringfurther user input enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device displays the secondaffordance (e.g., 618 a-4) in accordance with a determination that thesecond external device is not paired with the electronic device. In someembodiments, if the second external device is paired with the electronicdevice, the electronic device foregoes display of the second affordanceand, optionally, displays information (e.g., battery level) of thesecond external device. In some embodiments, the second affordance isdisplayed in a menu user interface (e.g., 636). In some embodiments, themenu user interface is a Bluetooth settings menu or an audio output menuuser interface of an audio media player application.

Note that details of the processes described above with respect tomethod 800 (e.g., FIG. 8) are also applicable in an analogous manner tothe methods described above and below. For example, method 700, method1000, and/or method 1200 optionally includes one or more of thecharacteristics of the various methods described above with reference tomethod 800. For example, operation 804 displaying the second userinterface in method 700 can be performed in response to detecting theindication in operation 708 of method 700. As another example, theoperations of method 800 can be performed prior to the operations ofmethod 1000 and/or method 1200. For brevity, these details are notrepeated below.

FIGS. 9A-9E illustrate exemplary user interfaces for adjusting a volumelevel of one or more devices, in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 10.

FIG. 9A illustrates device 600 concurrently connected to and providingaudio data to device 625 (via communication link C5) and device 650 (viacommunication link C6). Device 600 displays user interface 900 (e.g., ahome screen or application springboard) and detects input 910 a (e.g., aswipe on touch-sensitive display 602). In response to detecting input910 a, device 600 displays user interface 902 (e.g., a control center).User interface 902 includes affordances for controlling variousfunctions and setting of device 600 and peripheral devices connected todevice 600, such as device 625 and device 650. Affordance 902-1corresponds to an audio media application that is currently playing amedia item (Track 1 by DJ Appleseed). Volume affordance 902-2 providesthe ability to adjust the volume level of device 625 and device 650 fromuser interface 902 with a single input. In accordance with adetermination that device 600 is providing audio data to more than onedevice (e.g., sharing audio data with device 650 while concurrentlyproviding audio data to device 625), user interface 902 includesgraphical element 902-3 (e.g., a badge on volume affordance 902-2).Graphical element 902-3 provides a visual indication that device 600 isproviding audio data to multiple devices (e.g., devices associated withmultiple users).

In FIG. 9B, device 600 detects input 910 b (e.g., an upward drag)corresponding to selection of volume affordance 902-2. In accordancewith input 910 b being a first type of input (e.g., the upward dragillustrated in FIG. 9B), device 600 adjusts (e.g., increases) the volumelevel of device 625 and the volume level of device 650, as indicated bythe updated visual appearance of volume affordance 902-2 in FIG. 9C. Inthe embodiment illustrated in FIG. 9C, the height of the horizontal lineinside volume affordance 902-2 indicates a current master volume levelof device 625 and device 650. In some embodiments, adjusting the volumelevel for device 625 and device 650 with affordance 902-2 sets thevolume levels for device 625 and device 650 to the same volume level(e.g., even if device 625 and device 650 had different volume levelsprior to selection of affordance 902-2). In some embodiments, adjustingthe volume level for device 625 and device 650 with affordance 902-2sets the volume levels for device 625 and device 650 to respectivevolume levels based on the initial volume level of the respective deviceand the input on affordance 902-2 (e.g., the direction and length ofinput 910 b). In some embodiments, if the volume level of device 625 isthe same as the volume level of device 650, volume affordance 902-2indicates the volume level of device 625 and device 650. In someembodiments, if the volume level of device 625 is different from thevolume level of device 650, volume affordance 902-2 indicates the volumelevel of device 625, the volume level of device 650, the volume level ofthe device with the higher volume level, the volume level of the devicewith the lower volume level, or a combination (e.g., average) of thevolume levels of device 625 and device 650.

In FIG. 9C, device 600 detects input 910 c corresponding to selection ofvolume affordance 902-2. In accordance with input 910 c being a secondtype of input different from input 910 b, device 600 displays a userinterface, where the user interface that is displayed depends on aconnection condition with respect to an external device (e.g., device650).

In accordance with a determination that the connection condition issatisfied (e.g., device 650 is connected to device 600 concurrently withdevice 625), device 600 displays user interface 904, as shown in FIG.9D. User interface 904 includes graphical elements 904-1 through 904-4.Graphical element 904-1 represents device 625 and indicates that volumeaffordance 904-3 controls the volume level of device 625. Graphicalelement 904-2 represents device 650 and indicates that volume affordance904-4 controls the volume level of device 650. Affordance 904-3, whenselected (e.g., with a vertical drag), adjusts the volume level ofdevice 625 without changing the volume level of device 650. Affordance904-4, when selected (e.g., with a vertical drag), adjusts the volumelevel of device 650 without changing the volume level of device 625. Inthe embodiment illustrated in FIG. 9D, the volume level of device 625 isthe same as the volume level of device 650, which corresponds to thevolume level indicted by volume affordance 902-2.

In accordance with a determination that the connection condition is notsatisfied (e.g., device 650 is connected to device 600 via device 675),device 600 displays user interface 906, as shown in FIG. 9E. In FIG. 9E,device 625 is connected to device 600 via communication link C5; device675 is connected to device 600 via communication link C8; and device 650is connected to device 675 via communication link C7. In accordance withdevice 600, device 625, and device 675 being in this configuration, userinterface 906 includes graphical elements 906-1 through 9064. Graphicalelement 906-1 represents device 625 and indicates that volume affordance906-2 controls the volume level of device 625. User interface 906 doesnot include an affordance to control the volume level of device 650(e.g., since device 650 is connected to device 600 through device 675).For example, since device 650 is connected via communication link C7 todevice 675, device 675 maintains control over the volume level of device650 (e.g., the volume level of device 650 can only be controlled viainputs on device 675). Disconnect affordance 906-3, when selected,causes device 600 to cease sharing audio data with device 650 (e.g.,device 600 disconnects communication link C8 with device 675), asindicated by graphical element 906-4 (“Stop Listening with Chance”).

FIG. 10 is a flow diagram illustrating a method for adjusting a volumelevel of one or more devices using an electronic device in accordancewith some embodiments. Method 1000 is performed at a device (e.g., 100,300, 500, or 600) with a display device (e.g., 602). Some operations inmethod 1000 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1000 provides an intuitive way for adjustinga volume level of one or more devices. The method reduces the cognitiveburden on a user for adjusting a volume level of one or more devices,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to adjust a volumelevel of one or more devices faster and more efficiently conserves powerand increases the time between battery charges.

While a first connection condition is satisfied with respect to theelectronic device (e.g., 600), a first external device (e.g., 625), anda second external device (e.g., 650, 675) where the electronic device isconfigured to provide audio data to the first external device whenconnected to the first external device and to provide audio data to thesecond external device when connected to the second external device, theelectronic device receives (1002) a request (e.g., input 910 a) todisplay a first volume control affordance (e.g., 902-2). In someembodiments, the connection condition is based on a connection status ofthe first external device and/or the second external device to theelectronic device. In some embodiments, the connection condition issatisfied if the electronic device is concurrently connected to a firstexternal device (e.g., wireless headphones or a pair of wireless earbudsoperating as a single device) and a second external device (e.g.,wireless headphones or a pair of wireless earbuds operating as a singledevice) different from the first external device. In some embodiments,the electronic device is connected directly to the second externaldevice. In some embodiments, the electronic device is connected to thesecond external device via a third external device (e.g., a phone). Forexample, the electronic device is connected to the third externaldevice, and the third external device is connected to the secondexternal device. In some embodiments, the connection condition issatisfied only if the first external device and the second externaldevice are operating as independent devices (e.g., not as a pair ofearbuds operating together). Examples of a request to display the firstvolume control affordance include, but are not limited to, a touch inputon a touch-sensitive surface of the electronic device (e.g., an upwardswipe gesture from a bottom edge of the touch-sensitive surface, adownward swipe gesture from a top edge of the touch-sensitive surface),selection of an affordance, a press of a mechanical button on theelectronic device (e.g., while the electronic device is in a sleep stateor the display device is inactive), movement of the electronic devicethat satisfies a motion condition (e.g., picking up the electronicdevice or moving the electronic device into a viewing position). In someembodiments, the request to display the volume control affordanceincludes a request to display a user interface (e.g., a control centeruser interface) with the volume control affordance.

In response to receiving the request to display the first volume controlaffordance, the electronic device displays (1004) the first volumecontrol affordance (e.g., 902-2).

The electronic device detects (1006) an input (e.g., 910 c)corresponding to selection of the first volume control affordance. Insome embodiments, the input corresponding to selection of the volumecontrol affordance includes a contact on a touch-sensitive surface ofthe electronic device, where the contact is determined to have acharacteristic intensity that exceeds a predefined threshold intensity.In some embodiments, the input corresponding to selection of the volumecontrol affordance includes a contact on a touch-sensitive surface ofthe electronic device, where the contact is determined to have aduration that exceeds a predefined threshold duration.

In response to detecting the input corresponding to selection of thefirst volume control affordance, the electronic device displays (1008) auser interface (e.g., 904, 906). As part of displaying the userinterface, in accordance with a determination that a second connectioncondition is satisfied with respect to the second external device (e.g.,the second external device is connected directly to the electronicdevice; the second external device is not connected to the electronicdevice via a third external device (e.g., a phone); the second externaldevice is connected solely to the electronic device), the electronicdevice displays (1010) a second volume control affordance (e.g., 904-3)that, when selected, adjusts a volume level of the first external device(e.g., without adjusting the volume of the second external device) and athird volume control affordance (e.g., 904-4) that, when selected,adjusts a volume level of the second external device (e.g., withoutadjusting the volume of the first external device; the electronic devicedisplays separate controls for the first external device and the secondexternal device that provide the capability to control the volume levelof the first external device independently from the volume level of thesecond external device, and vice versa). In some embodiments, theelectronic device ceases display of the first volume control affordanceand displays the second volume control affordance and the third volumecontrol affordance. In some embodiments, the second connection conditionis satisfied with respect to the second external device if the secondexternal device is a compound device (e.g., a pair of earbuds operatingcooperatively as one device) and one or more of the elements of thecompound device is connected directly to the electronic device.Displaying a volume control affordance for the first external device anda separate volume control affordance for the second external devicebased on a determination that a connection condition is satisfied withrespect to the second external device provides feedback to the user bydisplaying controls that are relevant to the current context. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

As part of displaying the user interface, in accordance with adetermination that the second connection condition is not satisfied withrespect to the second external device, the electronic device displays(1012) a fourth volume control affordance (e.g., 906-2) that, whenselected, adjusts a volume level of the first external device (e.g.,without adjusting the volume of the second external device), withoutdisplaying a volume control affordance for adjusting the volume level ofthe second external device (e.g., the electronic device displays asingle volume control affordance to adjust the volume level of the firstexternal device). Displaying a volume control affordance for only thefirst external device based on a determination that the connectioncondition is not satisfied with respect to the second external deviceprovides feedback to the user by displaying controls that are relevantto the current context. Providing improved feedback enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the second connection condition is not satisfiedwith respect to the second external device if the second external deviceis paired to a third external device (e.g., a phone), and receives audiodata either directly from the electronic device or indirectly via thethird external device. In some embodiments, the second connectioncondition is not satisfied with respect to the second external device ifthe second external device is a pair of earbuds paired to a device otherthan the electronic device. In some embodiments, two devices are pairedif they have a persistent association with each other and are configuredto exchange data via a communication link. In some embodiments, devicesare not paired if they do not have a persistent association with eachother. In some embodiments, paired devices remain associated with eachother when a communication link between the devices is not currentlyactive, whereas devices that are temporarily connected but not pairedare not associated with each other after the temporary connection ends.In some embodiments, paired devices share common configuration settings.In some embodiments, the electronic device ceases display of the firstvolume control affordance and displays the fourth volume controlaffordance. In some embodiments, the user interface is displayed inaccordance with a determination that the input corresponding toselection of the first volume control affordance is a first type ofinput (e.g., a hard press or a static long press). In some embodiments,the first volume affordance provides the capability to simultaneouslyadjust the volume level of the first external device and the secondexternal device. For example, in some embodiments, in accordance with adetermination that the input corresponding to selection of the firstvolume control affordance is a second type of input (e.g., an upward ordownward swipe gesture on the first volume control affordance) differentfrom the first type, the electronic device updates the first volumecontrol affordance to indicate a new volume level and sends instructionsto adjust the volume level of the first external device and, if thesecond external device is not connected to a third external device, thevolume level of the second external device.

In some embodiments, the electronic device displays, concurrently withthe second volume control affordance (e.g., 616 a-3) and the thirdvolume control affordance (e.g., 616 a-4), a fifth volume controlaffordance (e.g., 616 a-6) that, when selected, adjusts a volume levelof the first external device and adjusts a volume level of the secondexternal device (see also, e.g., FIGS. 60 and 6Q). In some embodiments,the fifth volume control affordance is the first volume controlaffordance (e.g., the first volume control affordance remains displayedwhen it is selected).

In some embodiments, the input (e.g., 910 c) corresponding to selectionof the first volume control affordance includes a contact having acharacteristic intensity, and displaying the user interface (e.g., 904,906) is performed in accordance with a determination that thecharacteristic intensity exceeds a threshold intensity. In someembodiments, in accordance with a determination that the characteristicintensity does not exceed the threshold intensity, the electronic deviceforegoes displaying the user interface. Displaying the user interfacebased on a characteristic of the input provides additional controloptions for the first volume control affordance and avoids clutteringthe display with additional displayed controls. Providing additionalcontrol options without cluttering the display with additional displayedcontrols enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the electronic device displays, concurrently withthe first volume control affordance, an indication (e.g., 902-3) thatthe first connection condition is satisfied with respect to theelectronic device, a first external device, and a second externaldevice. In some embodiments, the indication that the first connectioncondition is satisfied with respect to the electronic device, a firstexternal device, and a second external device is displayed on the firstvolume control affordance.

In some embodiments, the electronic device displays, concurrently withthe fifth volume control affordance, a disconnect affordance (e.g.,906-3) that, when selected, disconnects the second external device fromthe electronic device. In some embodiments, the disconnect affordance isdisplayed concurrently with the fourth volume control affordance.Displaying an affordance for disconnecting the second external deviceprovides feedback that the user can cease sharing audio with the secondexternal device and presents the option to disconnect the secondexternal device without requiring additional inputs (e.g., to access aseparate options menu), thus reducing the number of inputs needed tocease sharing audio data. Providing improved feedback and reducing thenumber of inputs needed to perform an operation enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Note that details of the processes described above with respect tomethod 1000 (e.g., FIG. 10 are also applicable in an analogous manner tothe methods described above and below. For example, method 700, 800,and/or 1200 optionally includes one or more of the characteristics ofthe various methods described above with reference to method 1000. Forexample, the operations of method 1000 can be performed after theoperations of method 700 and/or method 800, and either before or afterthe operations of method 1200. For brevity, these details are notrepeated below.

FIGS. 11A-11F illustrate exemplary user interfaces for controlling anaudio media application, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIG. 12.

FIG. 11A illustrates device 1100 (e.g., a watch) with display device1102, rotatable input device 1104, and mechanical button 1106. In someembodiments, device 1100 is device 100, 300, or 500. In someembodiments, rotatable input device 1104 is depressible and rotatable.In FIG. 11A, device 1100 displays user interface 1108, which includesaffordance 1108-1 and affordance 1108-2. Affordance 1108-1 correspondsto an audio media application on a first device (e.g., a phone) withwhich device 1100 is connected (e.g., via a Bluetooth or internetconnection). In the embodiment illustrated in FIGS. 11A-11F, device 1100is connected (e.g., paired) with device 600 described above, andaffordance 1108-1 corresponds to an audio media application on device600. Affordance 1108-2 corresponds to an audio media application on asecond device (e.g., a wireless speaker) with which device 1100 isconnected (e.g., via a Bluetooth or internet connection). Affordance1108-1 and 1108-2 can be selected to display a user interface forcontrolling the corresponding application on the corresponding device.

In FIG. 11A, device 1100 detects input 1110 a (e.g., a tap)corresponding to selection of affordance 1108-1. In response todetecting input 1110 a, device 1100 displays audio media user interface1112 for controlling the audio media application on device 600corresponding to affordance 1108-1. Audio media user interface 1112includes, inter alia, track information 1112-1, volume level indicator1112-2, and controls 1112-3. Volume level indicator 1112-2 indicates thevolume level (or volume levels) of an audio output device (or audiooutput devices) to which device 600 is providing audio data. In someembodiments, the number of arcs on the right side of volume levelindicator 1112-2 indicates a volume level (e.g., one arc is LOW, twoarcs in MEDIUM, and three arcs is HIGH).

In FIG. 11B, device 1100 detects input 1110 b (e.g., a rotation ofrotatable input device 1104). In response to detecting input 110 b,device 1100 sends instructions to device 600 to adjust the volume levelof the device or devices outputting the audio provided by theapplication corresponding to audio media user interface 1112. Forexample, if device 600 is providing audio data concurrently to device625 and device 650 as described above, rotatable input device 1104 canbe rotated to adjust the volume levels for device 625 and device 650with a single input. In some embodiments, adjusting the volume level fordevice 625 and device 650 with rotatable input device 1104 sets thevolume levels for device 625 and device 650 to the same volume level(e.g., even if device 625 and device 650 had different volume levelsprior to movement of rotatable input device 1104). In some embodiments,adjusting the volume level for device 625 and device 650 with rotatableinput device 1104 sets the volume levels for device 625 and device 650to respective volume levels based on the initial volume level of therespective device and the movement of rotatable input device 1104 (e.g.,the amount and/or speed of rotation of rotatable input device 1104).

In accordance with a determination that the device corresponding toaudio media user interface 1112 is providing audio to multiple devices(e.g., device 600 is providing audio data to device 625 and device 650),device 1100 displays multiple volume level indicators in response todetecting input 1110 b. As shown in FIG. 11C, device 1100 displaysvolume level indicator 1112-4, which includes individual volume levelindicator 1112-4 a corresponding to a first output device (e.g., device625) and individual volume level indicator 1112-4 b corresponding to asecond output device (e.g., device 650). In response to detecting thatinput 1110 b has ceases (e.g., a predetermined amount of time afterdetecting that input 1110 b has ceased), device 1100 displays updatedvolume level indicator 1112-5 indicating a volume level after input 1110b, as shown in FIG. 1D. In some embodiments, if the volume level ofdevice 625 is the same as the volume level of device 650, volume levelindicator 1112-5 indicates the volume level of device 625 and device650. In some embodiments, if the volume level of device 625 is differentfrom the volume level of device 650, volume level indicator 1112-5indicates the volume level of device 625, the volume level of device650, the volume level of the device with the higher volume level, thevolume level of the device with the lower volume level, or a combination(e.g., average) of the volume levels of device 625 and device 650.

In FIG. 11D, device 1100 detects input 1110 c (e.g., a tap)corresponding to selection of affordance 1112-6 on user interface 1112.In response to detecting input 1110 c, device 1100 displays a userinterface for selecting an audio output device or devices. The userinterface depends on an output device condition based on, e.g., theconfiguration of available output devices.

For example, if device 600 is concurrently providing audio data to twodevices (device 625 and device 650), device 1100 displays deviceselection user interface 1114 as shown in FIG. 11E. Device selectionuser interface 1114 includes affordance 1114-1 and affordance 1114-2.Affordance 1114-1 corresponds to device 600 and, when selected, selectsdevice 600 as the device to output audio. Affordance 1114-2 correspondsto device 625 and device 650 and, when selected, selects both device 625and device 650 as devices to output audio. That is, selecting a singleaffordance (affordance 1114-2) causes audio data from the audio mediaapplication to be provided concurrently to more than one device (device625 and device 650).

If device 600 is not concurrently providing audio data to two devices(e.g., device is providing audio data to only device 625), device 1100displays device selection user interface 1116 as shown in FIG. 11F.Device selection user interface 1116 includes affordance 1116-1,affordance 1116-2, and affordance 1116-3. Affordance 1116-1 correspondsto device 600 and, when selected, selects device 600 as the device tooutput audio; affordance 1116-2 corresponds to device 625 and, whenselected, selects device 625 as devices to output audio; and affordance1116-3 corresponds to a third device to which device 600 is configuredto provide audio data. In some embodiments, there is no singleaffordance on device selection user interface 1116 that corresponds tomore than one device (e.g., there is no single affordance that causesaudio to be output on more than one device).

FIG. 12 is a flow diagram illustrating a method for controlling audiomedia output application using an electronic device in accordance withsome embodiments. Method 1200 is performed at a device (e.g., 100, 300,500, or 1100) with a display device (e.g., 1102). Some operations inmethod 1200 are, optionally, combined, the orders of some operationsare, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1200 provides an intuitive way forcontrolling audio media output. The method reduces the cognitive burdenon a user for controlling audio media output, thereby creating a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to control audio media output faster and moreefficiently conserves power and increases the time between batterycharges.

While displaying a first user interface (e.g., 1112) including controls(e.g., 1112-3) for an audio media application, the electronic devicereceives (1202) a request (e.g., input 1110 c) to display a userinterface (e.g., 1114, 1116) for selecting one or more devices (e.g.,wireless headphones or wireless earbuds) from which audio from the audiomedia application is to be output.

In response to receiving the request to display a user interface forselecting one or more devices from which audio from the audio mediaapplication is to be output, the electronic device displays (1204) asecond user interface (e.g., 1114, 1116).

As part of displaying the second user interface, in accordance with adetermination that a source electronic device (e.g., 600, 1100) isconnected to a first external device (e.g., 625; wireless headphones ora pair of wireless ear pods operating together as a single device) and asecond external device (e.g., 650; wireless headphones or a pair ofwireless earbuds operating as a single device), different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, the electronic device displays (1206) a firstaffordance (e.g., 1114-2) that, when selected, causes audio data fromthe audio media application to be provided concurrently to the firstexternal device and the second external device. Displaying a firstaffordance for causing audio data from the audio media application to beprovided concurrently to the first external device and the secondexternal device based on a determination that a source electronic deviceis connected to a first external device and a second external device,and that the source electronic device is configured to provide audiodata from the audio media application concurrently to the first externaldevice and the second external device, provides feedback to the user bydisplaying controls that are relevant to the current context. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the source electronic device is the electronicdevice. In some embodiments, the source electronic device is an externaldevice connected to the electronic device. In some embodiments, theaudio media application is running on a source device external to theelectronic device, and the audio media application is controllable byinput at the electronic device via the connection between the electronicdevice and the source device. In some embodiments, audio is not providedto the second external device via the first external device. In someembodiments, the second external device appears to the electronic deviceas a separate external device from the first external device. In someembodiments, the first external device and the second external deviceare not a pair of earbuds that operate as a single device.

As part of displaying the second user interface, in accordance with adetermination that the source electronic device is connected to thefirst external device and configured to provide audio data from theaudio media application to the first external device withoutconcurrently providing audio data from the audio media application toanother external device, the electronic device displays (1208) a secondaffordance (e.g., 1116-2) that, when selected, causes audio data fromthe audio media application to be provided solely to the first externaldevice. Displaying a second affordance for causing audio data from theaudio media application to be provided solely to the first externaldevice based on a determination that a source electronic device isconnected to a first external device and configured to provide audiodata from the audio media application to the first external device,without concurrently providing audio data from the audio mediaapplication to another external device, provides feedback to the user bydisplaying controls that are relevant to the current context. Providingimproved feedback enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, if the source electronic device is connected tomultiple output devices (e.g., the first external device and the secondexternal device) and is configured to provide audio data from the audiomedia application to each of the output devices, but not concurrently tomore than one at a time, the electronic device displays one affordancefor each output device to provide audio data to the corresponding outputdevice. In some embodiments, providing audio solely to the firstexternal device includes providing audio to a pair of physicallyseparated earbuds that operate as a single external device.

In some embodiments, the first external device (e.g., 625) is pairedwith the source electronic device (e.g., 600, 1100). In someembodiments, two devices (e.g., the first external device and the sourceelectronic device) are paired if they have a persistent association witheach other and are configured to exchange data via a communication link.In some embodiments, devices are not paired if they do not have apersistent association with each other. In some embodiments, paireddevices remain associated with each other when a communication linkbetween the devices is not currently active, whereas devices that aretemporarily connected but not paired are not associated with each otherafter the temporary connection ends. In some embodiments, paired devicesshare common configuration settings.

In some embodiments, the second external device (e.g., 650) is notpaired with the source electronic device (e.g., 600, 1100). In someembodiments, the source electronic device (e.g., 600) is paired with theelectronic device (e.g., 1100).

In some embodiments, the second user interface includes a thirdaffordance (e.g., 1114-1, 1116-1) that, when selected, causes audio fromthe audio media application to be outputted by the source electronicdevice.

In some embodiments, the electronic device detects an input (e.g., asingle input; a single input on a single volume adjustment affordance).In some embodiments, in response to detecting the input (e.g., 1110 b),the electronic device adjusts a volume level of the first externaldevice and adjusts a volume level of the second external device.Adjusting a volume level of the first external device and a volume levelof the second external device in response to a single input reduces thenumber of inputs needed to adjust the volume of both devices and reducesthe need to display additional controls to adjust the volume of bothdevices. Reducing the number of inputs needed to perform an operationand providing additional control options without cluttering the userinterface with additional displayed controls enhances the operability ofthe device and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in response to detecting the input, the electronicdevice displays a graphical indication (e.g., 1112-4 a) of the volumelevel of the first external device and a graphical indication (e.g.,1112-4 b) of the volume level of the second external device differentfrom the graphical indication of the volume level of the first externaldevice. In some embodiments, the graphical indications of the volumelevels of the first and second external devices are visually distinctgraphical elements (e.g., separate sliders or bars). Displaying separategraphical indications of the volume level for each device providesfeedback to the user that the input adjusts the volume of both devices.Providing improved feedback enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the input includes rotation of a rotatable inputdevice (e.g., 1104) of the electronic device that rotates relative to ahousing of the electronic device. In some embodiments, the rotatableinput device is rotatable and depressible.

Note that details of the processes described above with respect tomethod 1200 (e.g., FIG. 12) are also applicable in an analogous mannerto the methods described above. For example, method 700, 800, and/or1000 optionally includes one or more of the characteristics of thevarious methods described above with reference to method 1200. Forexample, the operations of method 1200 can be performed before or afterthe operations of method 700 and/or method 800, and either before orafter the operations of method 1000. For brevity, these details are notrepeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of audio media. The present disclosure contemplatesthat in some instances, this gathered data may include personalinformation data that uniquely identifies or can be used to contact orlocate a specific person. Such personal information data can includedemographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, account information and/or userpreferences for audio media services (e.g., streaming music services),data or records relating to a user's health or level of fitness (e.g.,vital signs measurements, medication information, exercise information),date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide audio media that is of greater interest to the user.Accordingly, use of such personal information data enables users to havecalculated control of the provided content. Further, other uses forpersonal information data that benefit the user are also contemplated bythe present disclosure. For instance, health and fitness data may beused to provide insights into a user's general wellness, or may be usedas positive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof streaming audio services, the present technology can be configured toallow users to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In another example, users can select not toprovide user preferences or account information for streaming audioservices. In yet another example, users can select to limit the lengthof time preference data is maintained or entirely prohibit thedevelopment of a baseline preference profile. In addition to providing“opt in” and “opt out” options, the present disclosure contemplatesproviding notifications relating to the access or use of personalinformation. For instance, a user may be notified upon downloading anapp that their personal information data will be accessed and thenreminded again just before personal information data is accessed by theapp.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, audio contentcan be selected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to theaudio content delivery services, or publicly available information.

What is claimed is:
 1. An electronic device, comprising: a displaydevice; one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: while displaying a first userinterface including controls for an audio media application, receiving arequest to display a user interface for selecting one or more devicesfrom which audio from the audio media application is to be output; inresponse to receiving the request to display a user interface forselecting one or more devices from which audio from the audio mediaapplication is to be output, displaying a second user interfaceincluding: in accordance with a determination that a source electronicdevice is connected to a first external device and a second externaldevice, different from the first external device, and configured toprovide audio data from the audio media application concurrently to thefirst external device and the second external device, displaying a firstaffordance indicating that audio data from the audio media applicationis configured to be provided concurrently to the first external deviceand the second external device; and in accordance with a determinationthat the source electronic device is connected to the first externaldevice and configured to provide audio data from the audio mediaapplication to the first external device without concurrently providingaudio data from the audio media application to another external device,displaying a second affordance indicating that audio data from the audiomedia application is configured to be provided solely to the firstexternal device.
 2. The electronic device of claim 1, wherein the firstexternal device is paired with the source electronic device.
 3. Theelectronic device of claim 1, wherein the second external device is notpaired with the source electronic device.
 4. The electronic device ofclaim 1, wherein the source electronic device is paired with theelectronic device.
 5. The electronic device of claim 4, wherein thesecond user interface includes a third affordance that, when selected,causes audio data from the audio media application to be outputted bythe source electronic device.
 6. The electronic device of claim 1,wherein the one or more programs further include instructions for:detecting an input; and in response to detecting the input, adjusting avolume level of the first external device and adjusting a volume levelof the second external device.
 7. The electronic device of claim 6,wherein the one or more programs further include instructions for: inresponse to detecting the input, displaying a graphical indication ofthe volume level of the first external device and a graphical indicationof the volume level of the second external device different from thegraphical indication of the volume level of the first external device.8. The electronic device of claim 6, wherein the input includes rotationof a rotatable input device of the electronic device that rotatesrelative to a housing of the electronic device.
 9. A non-transitorycomputer-readable storage medium storing one or more programs configuredto be executed by one or more processors of an electronic device with adisplay device, the one or more programs including instructions for:while displaying a first user interface including controls for an audiomedia application, receiving a request to display a user interface forselecting one or more devices from which audio from the audio mediaapplication is to be output; in response to receiving the request todisplay a user interface for selecting one or more devices from whichaudio from the audio media application is to be output, displaying asecond user interface including: in accordance with a determination thata source electronic device is connected to a first external device and asecond external device, different from the first external device, andconfigured to provide audio data from the audio media applicationconcurrently to the first external device and the second externaldevice, displaying a first affordance indicating that audio data fromthe audio media application is configured to be provided concurrently tothe first external device and the second external device; and inaccordance with a determination that the source electronic device isconnected to the first external device and configured to provide audiodata from the audio media application to the first external devicewithout concurrently providing audio data from the audio mediaapplication to another external device, displaying a second affordanceindicating that audio data from the audio media application isconfigured to be provided solely to the first external device.
 10. Thenon-transitory computer-readable storage medium of claim 9, wherein thefirst external device is paired with the source electronic device. 11.The non-transitory computer-readable storage medium of claim 9, whereinthe second external device is not paired with the source electronicdevice.
 12. The non-transitory computer-readable storage medium of claim9, wherein the source electronic device is paired with the electronicdevice.
 13. The non-transitory computer-readable storage medium of claim12, wherein the second user interface includes a third affordance that,when selected, causes audio data from the audio media application to beoutputted by the source electronic device.
 14. The non-transitorycomputer-readable storage medium of claim 9, wherein the one or moreprograms further include instructions for: detecting an input; and inresponse to detecting the input, adjusting a volume level of the firstexternal device and adjusting a volume level of the second externaldevice.
 15. The non-transitory computer-readable storage medium of claim14, wherein the one or more programs further include instructions for:in response to detecting the input, displaying a graphical indication ofthe volume level of the first external device and a graphical indicationof the volume level of the second external device different from thegraphical indication of the volume level of the first external device.16. The non-transitory computer-readable storage medium of claim 14,wherein the input includes rotation of a rotatable input device of theelectronic device that rotates relative to a housing of the electronicdevice.
 17. A method comprising: at an electronic device with a displaydevice: while displaying a first user interface including controls foran audio media application, receiving a request to display a userinterface for selecting one or more devices from which audio from theaudio media application is to be output; in response to receiving therequest to display a user interface for selecting one or more devicesfrom which audio from the audio media application is to be output,displaying a second user interface including: in accordance with adetermination that a source electronic device is connected to a firstexternal device and a second external device, different from the firstexternal device, and configured to provide audio data from the audiomedia application concurrently to the first external device and thesecond external device, displaying a first affordance indicating thataudio data from the audio media application is configured to be providedconcurrently to the first external device and the second externaldevice, and in accordance with a determination that the sourceelectronic device is connected to the first external device andconfigured to provide audio data from the audio media application to thefirst external device without concurrently providing audio data from theaudio media application to another external device, displaying a secondaffordance indicating that audio data from the audio media applicationis configured to be provided solely to the first external device. 18.The method of claim 17, wherein the first external device is paired withthe source electronic device.
 19. The method of claim 17, wherein thesecond external device is not paired with the source electronic device.20. The method of claim 17, wherein the source electronic device ispaired with the electronic device.
 21. The method of claim 20, whereinthe second user interface includes a third affordance that, whenselected, causes audio data from the audio media application to beoutputted by the source electronic device.
 22. The method of claim 17,further comprising: detecting an input; and in response to detecting theinput, adjusting a volume level of the first external device andadjusting a volume level of the second external device.
 23. The methodof claim 22, further comprising: in response to detecting the input,displaying a graphical indication of the volume level of the firstexternal device and a graphical indication of the volume level of thesecond external device different from the graphical indication of thevolume level of the first external device.
 24. The method of claim 22,wherein the input includes rotation of a rotatable input device of theelectronic device that rotates relative to a housing of the electronicdevice.